1.2. Summary
Overall, the specific items tested went well. Not all of the specification was tested — what was tested did not point out any specific issues with the draft.
Items of note are:
Access Control Lists are not yet supported by any of the servers or clients.
Clients and servers both had some issues with respect to their implementation of the draft components. Several of those items were fixed during the testing. All clients still have some components that are not yet working and are still under development.
Two servers support the majority of the items selected for testing during this event. The third server supports less but is well on its way towards being a robust CalDAV server.
With regards to RFC2445, the iCalendar specification, there appears to be an issue with recurring rules with
DTSTARTin UTC. While it is not valid in RFC2445, several of the vendors supportDTSTARTin UTC. Therefore, this issue needs to be addressed — either the RFC2445 must be changed or the vendors need to change their applications to support the current RFC2445. This is an issue that will be turned over to the Calsify technical group as it will be pertinent to the simplification work going on for RFC2445.Going forward, we need to get additional vendors into the testing group. It would be good to see if we can find additional mobile vendors for testing as well. The consortium will be looking into ways of expanding the number of vendors that participate during interoperability events. The more we test, the more we ensure a good specification.
In order to move the draft to proposed standard level within the IETF (after it becomes an RFC), we will need to test all the
MUSTs/SHOULDs/MUST NOTs/SHOULD NOTs in the draft in order to be considered interoperable. Pat Egen, the interop manager, volunteered to put together a matrix of these components and will post this on the public CalConnect server.
Finally, the following are comments by two of the participants stating how they felt the interop went overall.